Inspect cached objects for questionable members#6658
Merged
labkey-adam merged 7 commits intodevelopfrom May 20, 2025
Merged
Conversation
labkey-matthewb
approved these changes
May 15, 2025
Contributor
|
Quick manual testing looks good. I did notice the the log entries created in the catch blocks end up looking a bit mysterious. A longer message might be be helpful. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
Cached objects can end up holding stale Containers, Users, etc. In general, we want cached objects to hold IDs and retrieve these objects from their own caches as needed.
https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=53058
Related Pull Requests